Method and a system for the deterministic autoconfiguration of a device

ABSTRACT

A method for deterministic auto-configuration of a device upon connection to an apparatus includes as a first step, during a first-time connection of the device to the apparatus, a generation of a device-specific configuration data structure, wherein this configuration data structure identifies the configuration data of the device and/or the apparatus, which configuration data was determined during a first-time connection of the device to the apparatus. The next step is storing of the configuration data structure in the device and/or in the apparatus. During a renewed connection of the device to the apparatus, the first-time configuration data of the device and/or the apparatus is determined by means of the configuration data structure, and the device and/or the apparatus correspondingly furnishes the first-time configuration data. The system is equipped in such a way as to execute the stated method.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to PCT Application No.PCT/EP2015/057207, having a filing date of Apr. 1, 2015, based off of DEApplication No. 102014206989.0 having a filing date of Apr. 11, 2014,the entire contents of which are hereby incorporated by reference.

FIELD OF TECHNOLOGY

The following relates to an apparatus and a method for the deterministicautoconfiguration of a device in the course of connection to anapparatus.

BACKGROUND

An automatic configuration of a device in the course of connection toanother device or an apparatus, which is also designated asplug-and-play functionality, is known in the case of computers, whichare supplemented, for example, by additional internal or externalcomponents, such as, for example, a memory expansion, a hard drive, or acomputer mouse. An automatic configuration of devices via an IP-basednetwork is also known, for example under the designation “universalplug-and-play”. However, autoconfiguration, or plug-and-playfunctionality, also plays an important role in automation systems. Bythe autoconfiguration of field and control devices an automation systemcan easily be set up. DE 10 2010 063 437 A1 describes, for example, amethod for the configuration of one or a plurality of devices in anEthernet-based communications network with which a location-dependentautomatic configuration of the devices is enabled in a simple manner.

There exists on the other hand, however, the requirement that anautomation system, for example, or even a train control and traincommunications system, functions reliably. For this purpose a fixedconfiguration would be advantageous. Regulations can also require thatonly one particular inspected and approved configuration is used inregular operation.

To utilize the requirements for stable network operation withfunctioning or else authorized configurations for devices that are onlyplugged into an apparatus or connected to the latter temporarily, andmay also be required to be plugged into various apparatuses a number oftimes, the previous autoconfiguration methods are not suitable. Forexample, in some operating systems, such as Windows 7, or firmware, suchas for example, the BIOS, a non-volatile database is used for extendedsystem configuration data (ESCD), which stores plug-and-playconfigurations. The said ESCD database is used by the operating systemto allocate resources and configuration data for devices such asexpansion components. The operating system updates such a configurationdatabase whenever the hardware configuration alters after a newallocation of resources is determined. Thus, in the event of a temporaryunplugging and a later reconnection of the device to the apparatus, anautomatic configuration of the device is not ensured that the device isconnected with the same configuration that was used previously.

SUMMARY

An aspect relates to adjusting the flexibility of an autoconfigurationfunction, for example, when applied in an automation environment, suchthat stable operation is ensured.

The inventive method for the deterministic autoconfiguration of a devicein the course of connection to an apparatus comprises as a first stepthe generation of a device-specific configuration data structure in theevent of a first-time connection of the device to the apparatus, whereinthe said configuration data structure identifies the configuration dataof the device and/or the apparatus, which configuration data have beendetermined in the course of a first-time connection of the device to theapparatus. The next step is the storage of the configuration structurein the device and/or in the apparatus. In the event of a renewedconnection of the device to the apparatus, the first-time configurationdata of the device and/or the apparatus are determined by means of theconfiguration data structure, and the device and/or the apparatus is/areset up in accordance with the first-time configuration data.

A first-time connection is characterized in that no configuration datastructure is present that can be assigned to the apparatus and/or to thedevice. In the context of embodiments of the invention, a first-timeconnection can therefore e.g. also exist if a stored configuration datastructure has been deleted, or marked as invalid, or if to dateconnections have only been made in which no configuration data structurehas been generated and stored.

This enables a device or the apparatus, into which the device isplugged, or to which the device is connected, to be configured in thesame manner as was the case in a first-time connection of the device tothe apparatus. Thus a device can be flexibly deployed, and when it isreconnected to the apparatus its previous configuration can simply bereproduced.

In an advantageous form of an embodiment, fixedly prescribed deviceidentification information, which is transmitted from the device atleast in the case of the first-time connection to the apparatus for thepurposes of identifying the device, is recorded in the configurationdata structure and the first-time configuration data of the deviceand/or the apparatus are determined by means of the deviceidentification information.

This makes it possible for no information concerning the first-timeconfiguration data or else only the configuration data structure to bestored on the device itself. In the event of a renewed connection of thedevice to the apparatus, and the transmission of the deviceidentification information from the device to the apparatus, thefirst-time configuration data can be identified by means of the deviceidentification information in the apparatus, and can be transmitted tothe device. The device can thus be a component with a simple structure,for example, a sensor in an automation network, which does not need anymemory capacity for the purposes of storing a configuration datastructure or the first-time configuration data itself. All that isneeded is memory capacity in the apparatus for the configuration datastructure and the first-time configuration data.

In a further form of an embodiment, the configuration data structurecomprises a configuration identifier, which is determined in the courseof a first-time connection of the device to the apparatus.

If, for example, the configuration data structure is stored in thedevice and in the apparatus, then, in the event of a renewed connectionof the device to the apparatus, the device can transmit theconfiguration identifier to the apparatus, and via the configurationidentifier can determine the associated first-time configuration data inthe apparatus. The configuration data are then transferred to thedevice, and the device, and possibly also the apparatus, is configuredin accordance with the configuration data. This makes possible a simplystructured look-up table in the apparatus, and thus an autoconfigurationof the device and the apparatus that can be executed in a short periodof time. Thus, the same configuration identifier can be used for variousdevices with, for example, various items of device identificationinformation, since in the event of a renewed connection of the device tothe apparatus the configuration data are identified by means of theconfiguration identifier, and not, for example, by means of the deviceidentification information itself.

In an advantageous form of an embodiment, the configuration datastructure comprises the configuration data of the device and/or theapparatus.

Here, in the event of a renewed connection of the device to theapparatus, a check must simply be made as to whether the sameconfiguration data structure is present in the device and also in theapparatus. A transfer of the configuration data itself is not necessary,since these are already contained in the configuration data structure.The device and the apparatus can implement the appropriate configurationindependently.

In a further advantageous form of an embodiment, the configuration datastructure comprises a hash value of the configuration data, and thesetting up of the device and/or the apparatus with the reactivatedconfiguration data is then solely executed if the hash value of thereactivated configuration data agrees with the hash value in theconfiguration data structure.

By this means, any alteration or manipulation of the configuration datain the device and/or in the apparatus can be detected, and anyimplementation of an altered or manipulated configuration can thus bedetected and prevented.

In an advantageous form of an embodiment, the configuration data arestored only after a successful test of the configuration.

By this means, a functioning configuration is ensured, both in the caseof the first-time connection, and also in the event of any subsequentconnection of the device to the apparatus.

In an advantageous form of an embodiment, the configuration datastructure comprises information concerning the type of the device.

In the event of connection of another device of the same type to theapparatus, the other device can be automatically configured inaccordance with the configuration data of a configuration data structurethat is already present for the same type of device.

Thus, for example, in the course of a changeover of device or componenta transfer of the data for the previous device of the same type can beexecuted automatically. By this means, for example, a simple changeoverof a replacement part with subsequent autoconfiguration can be executedin accordance with the previous device that has been exchanged.

In an advantageous form of an embodiment, the configuration datastructure comprises an item of information concerning a predeterminedplant configuration version, and only a connection of device andapparatus with the same plant configuration identifier is authorized.

By this means, it can be ensured that an autoconfiguration is onlyexecuted between devices and/or apparatuses with identical configurationstate. As a result it is impossible to connect together arbitrarydevices.

In an advantageous form of an embodiment, the configuration datastructure is stored only after a successful function test, and/or aftera successful comparison of the device identification information and/orconfiguration data with previously configured data, and/or after aconfirmation by an administrator.

With a recording of the configuration data structure after a successfulfunction test, it is achieved that an identical configuration isreliably reactivated in the course of each replugging-in. If theconfiguration data structure is only stored after a successfulcomparison of the device identification information and/or theconfiguration data with previously configured data, then security rulescan be linked with the identifiers, which rules must exist for anautoconfiguration. The confirmation of an administrator can, forexample, ensure that devices that have not yet been connected to datecan only be connected to an apparatus in a particular mode of operation,for example in a maintenance mode of the plant.

In an advantageous form of an embodiment, further configuration datastructures with further related configuration data can be determined andstored for a device.

This enables various configurations to be authorized for adevice/apparatus combination. Here, the said various configurations canbe selected as a function of further parameters such as, for example,various plant configuration identifiers, so that a device can operatetogether with an apparatus in various plant configurations.

In an advantageous form of an embodiment, a device can be configuredsolely with the first-time configuration data structure and the relatedconfiguration data.

In an advantageous form of an embodiment, the configuration datastructure has a temporal period of validity, which is prescribed by thedevice and/or by the apparatus.

In an advantageous form of an embodiment, after the expiry of a periodof validity the configuration data structure is identified as stopped,or deleted.

In an advantageous form of an embodiment, the configuration datastructure has a spatial period of validity, and a renewed connection ofthe device to the apparatus is only possible in the geographical regionthat corresponds to the spatial validity data.

In an advantageous form of an embodiment, the configuration datastructure is used for the purposes of authenticating and/or authorizingthe device and/or the apparatus in a subsequent communicationsconnection.

By means of the configuration data structure, the exact device/apparatuscombination is characterized and authenticated.

In a further advantageous form of an embodiment, the configuration datastructure is used in the course of a key exchange in a subsequentcommunications connection of the device and/or the apparatus.

The inventive system for the deterministic autoconfiguration of a devicein the course of connection to an apparatus comprises at least onedevice and at least one apparatus, wherein the device and the apparatusare designed so as to generate a device-specific configuration datastructure in the event of a first-time connection of the device to theapparatus, wherein the said configuration data structure identifies theconfiguration data of the device and/or of the apparatus, whichconfiguration data have been determined in the course of a first-timeconnection of the device to the apparatus. Furthermore, the device andthe apparatus are designed so as to store the configuration datastructure in the device and/or in the configuration, and in the event ofa renewed connection of the device to the apparatus, determine thefirst-time configuration data of the device and/or the apparatus bymeans of the configuration data structure, and set up the device and/orthe apparatus in accordance with the reactivated first-timeconfiguration data.

Thus, in particular a functioning and tested configuration can bereproduced in the course of a renewed connection of the device to theapparatus, and can thus ensure the proper functioning of the apparatuswith the device.

In an advantageous form of an embodiment of the system, the device is aninternal component of the apparatus that can be plugged into anapparatus, or the device is a pluggable peripheral component of anapparatus, or the device is a network component, or an application on anetwork component, which is connected to the apparatus, which is acommunications network with network components and/or control units.

Furthermore, a device and an apparatus are claimed, which are designedso as to execute the method as claimed in claims 1 to 16. Furthermore, acomputer program product is claimed with program commands for thepurposes of executing the method.

BRIEF DESCRIPTION

Some of the embodiments will be described in detail, with reference tothe following figures, wherein like designations denote like members,wherein:

FIG. 1 shows a first example of embodiment of an inventive system in aschematic representation;

FIG. 2 shows a second example of embodiment of an inventive system withadditional servers for the purposes of determining configuration data ina schematic representation;

FIG. 3 shows an example of embodiment of an inventive configuration datastructure in a schematic representation; and

FIG. 4 shows an example of embodiment of the inventive method as a flowchart.

In all figures the parts corresponding to one another are allocated thesame reference symbols.

DETAILED DESCRIPTION

By means of FIGS. 1 and 2 various systems are shown, in which anautoconfiguration of a device takes place in the course of connection toan apparatus. Hereinafter the terms “connect” and “plug in” are usedsynonymously.

The system 10 comprises various external devices 13.1, 13.4, which can,for example, be plugged into an apparatus 11 as pluggable peripheralcomponents. Furthermore, a device 12, for example, an expansion card, isconnected to the apparatus 11 as a pluggable internal component. Theapparatus 11 can be, for example, a control device within an automationplant. The latter is connected to an automation network, here to thecommunications network 15. By means of autoconfiguration, sensors and/oractuators, here, for example, the devices 13.1, 13.4, can be connectedto the apparatus 11, i.e. the control device. An expansion module, herethe device 12, for example an input-output module, can also be connectedto the apparatus 11, i.e. to the control device, by means ofautoconfiguration. Sensors and/or actuators 13.2, 14.2 can in turn beplugged into the expansion module 12. In this case the expansion module12 has the role of an apparatus, to which devices 13.2, 14.2 areconnected.

In order that the apparatus 11, 12 can operate together with theconnected devices 13.1, 14.1, and/or 13.2, 14.2, the devices 13.1, 14.1and the apparatus 11 must be configured appropriately, i.e.communications parameters, such as, e.g. port numbers or addresses, mustbe arranged, for example, between the apparatus 11 and the device 13.1,14.1. Furthermore, certain control functions in the devices 13.1, 14.1can be activated and thus configured for the purposes of executingcertain tasks in conjunction with the apparatus. Correspondinglyadjustments can be made to the configuration of the apparatus 11, oralso to further components, connected, for example, via thecommunications network 15.

In a first-time autoconfiguration procedure, a connection is madebetween a device and an apparatus, wherein the device is identified bythe apparatus, and as a result the apparatus determines a configuration,and the said configuration is communicated to the device and activated,in order to utilize the device. This is represented in FIG. 2 with theexample of a device 23, which is connected into a distributed system 20,for example, an automation network. Here the apparatus 21 is to beunderstood to be the communications network 15, with network componentsand/or control units, such as, for example, a configuration server 22 ora context server 27. After the device 23 has been connected via acommunications network 15 to the apparatus 21, the device 23 establishescontact with, for example, the configuration server 22, and transfersdevice identification information ID and possibly further attributesAtts to the server 22. An autoconfiguration unit 25 in the configurationserver 22 checks, for example by means of a security directive, whetherthe device 23 may be connected to the apparatus 21. Furthermore, theserver 22, by interrogating a context server 27, can check whether, forexample, a connection between the device 23 and the apparatus 21 isallowed in the current operating state of the system. If this is thecase, a configuration unit 25 determines, for example, the configurationdata CONFIG for the device 23, together with a device-specificconfiguration data structure KDS, and transmits these via thecommunications network 15 to the device 23. The exchange of messages issymbolized in FIG. 2 by the arrows.

The device 23 is subsequently configured in accordance with the receivedconfiguration data CONFIG. Here the configuration data structure KDS isstored either in the device 23, for example in a memory 24 provided forthis purpose, or in the apparatus 21, for example in the configurationunit 25 in the configuration server 22, or in both.

If the device 23 is now separated from the apparatus 21, and at a laterpoint in time is reconnected to the apparatus 21, the first-timeconfiguration data CONFIG of the device 23 and/or the apparatus 21 aredetermined by means of the configuration data structure KDS, and thedevice 23 and/or the apparatus 21 are set up corresponding to thereactivated first-time configuration data. Here the configuration datacan also relate to further network components, which must be adjusted inthe course of a connection of the device 23 to the apparatus 21. Thesaid configuration data are communicated to the other appropriatenetwork components.

What is important in the event of a renewed connection of the device 23to the apparatus 21 is the fact that the same configuration data arereused as in the case of the first-time connection of the device 23 tothe apparatus 21. Here the configuration data structure KDS identifiesthe said first-time configuration and/or the corresponding configurationdata.

In order to guarantee a functional system 10, 20, in an example ofembodiment only such first-time configuration data and a relatedconfiguration data structure KDS are stored, if the correspondingconfiguration of the device and/or the apparatus has previously beentested successfully.

The configuration data structure KDS, as represented, for example, inFIG. 3, can thereby comprise various items of information and/orparameters, and according to the parameters and/or items of informationincluded can be stored either in the device 23, or in the apparatus, orin both. In FIG. 3 an exemplary configuration data structure KDS isrepresented. The configuration data structure KDS comprises at least oneor also a combination of the parameters and/or items of informationshown.

In a first example of an embodiment, in the course of the first-timeconnection of the device 23 to the apparatus 21, for example in theconfiguration server 22 in FIG. 2, the configuration data are determinedfor the device and/or the apparatus 21.

Furthermore, a configuration data structure KDS is generated, whichcomprises, for example, the device identification information 31 of thedevice 23. Identified by the configuration data structure KDS, theconfiguration data determined are now stored, for example in aconfiguration unit 25 of the configuration server 22. In the event of arenewed connection of the device 23 to the apparatus 21, the device 23transmits the device identification information 31 to the apparatus 21.Thereupon the apparatus 21 determines the configuration data structureKDS with the corresponding device identification information 31 and theconfiguration data additionally stored. These are transmitted to thedevice 23 and the device is there set up accordingly.

In addition, a hash value 34 can be contained in the configuration datastructure KDS; this has been formed from the first-time configurationdata. In this case the device 23 reactivates the first-timeconfiguration data only if a hash value, formed by the device 23 via theconfiguration data delivered from the apparatus 21, agrees with the hashvalue 34 in the configuration data structure. Thus any alteration of theconfiguration data sent from the apparatus, compared with the first-timeconfiguration data, is detected, and any implementation is prevented.

The configuration data structure KDS can also contain a configurationidentifier 32. Instead of the device identification information 31 thesaid configuration identifier 32 can be transmitted in the event of arenewed connection of the device 23 to the apparatus 21. In this casethe first-time configuration data of the device 23 can also beidentified in the apparatus 21 with this configuration identifier 32 andstored accordingly.

In addition, the configuration data structure KDS can compriseinformation concerning the type 33 of the device 23. If the device 23transmits the said configuration data structure KDS in the course of arenewed connection to the apparatus 21, a transfer of configuration dataof the same device type can take place, dependent, for example, upon asecurity directive set up in the system 22. This makes possible, forexample, the exchange of identical devices, or of replacement parts,which are configured in accordance with the previous device. If thedevice 23 delivers an item of information concerning the device type 33for which no first-time configuration data are present in the apparatus21, an error message or an alarm is outputted.

The configuration data structure KDS can comprise further informationsuch as, for example, a plant configuration identifier 36. The latter isutilized for the purpose of executing only one autoconfiguration ofdevice and apparatus with a particular, and/or with an identical, plantconfiguration state, which is expressed in terms of the same plantconfiguration identifier 36. Thus it is ensured that only devices with,for example, the same configuration version, that is to say, with thesame configuration state, are used in a plant.

The configuration data structure KDS can comprise further parameters 37,for example, a temporal period of validity or spatial validity data. Thetemporal period of validity can be prescribed by the device 23 and/or bythe apparatus 21. After expiry of the period of validity theconfiguration data structure KDS is identified as blocked, or deleted.In this manner a later unintentional reactivation of the configurationdata in the course of connecting the device to the apparatus is nolonger possible. Similarly devices 23 are thus prevented from beingconfigured with an outdated configuration and newly introduced into asystem.

By virtue of the spatial validity data the execution of anautoconfiguration with the stored first-time configuration data is onlynewly authorized if the configuration of the device takes place in apredetermined spatial environment, for example in the same environmentas in the case of the first-time configuration, in the course of whichthe configuration data structure KDS and the related first-timeconfiguration data have been stored.

However, a configuration data structure KDS can also contain theconfiguration data itself, and/or a description of the configurationdata 35. If such a configuration data structure KDS with a descriptionof the configuration data 35 is generated in the course of a first-timeconnection of the device 23 to the apparatus 21, and is stored both inthe device and in the apparatus, in the event of a later renewedconnection of the device 23 to the apparatus 21 all that is necessaryis, for example, the transmission of one of the parameters of theconfiguration data structure KDS from the device 23 to the apparatus 21,and a confirmation of the said parameter of the configuration datastructure by the apparatus 21. Thereupon the device 23 can independentlyextract the configuration data 35 from the configuration data structureKDS and implement the same. For its part the apparatus 21 can do thesame. By this means the quantity of data to be transferred is reduced,less bandwidth is required, and any manipulation of the configurationdata on the transfer path is prevented.

If in contrast to the above only the device identification information31 is contained in the configuration data structure KDS, and in theapparatus a linking of the device identification information 31 with thefirst-time configuration data, then even very simply structured devices23 can execute a deterministic autoconfiguration, since only the deviceidentification information 31 needs to be stored on the device, but notany other configuration data. The latter are transmitted from theapparatus 21 to the device 23.

In one form of an embodiment, the configuration data structure KDS isonly stored in the device 23 and/or in the apparatus 21 after asuccessful function test. This ensures that an identical configurationis reliably reactivated in the course of each further plugging of thedevice 23 into the apparatus 21. However, the configuration datastructure KDS can also only agree with previously established data, forexample, from planning data and/or with a previously established systemconfiguration, after a successful comparison of the deviceidentification information 31 and/or the configuration data. However,the storage of the configuration data structure KDS can also take placeonly if the latter is confirmed by an administrator. Thus it can comeabout, for example, that a device that has not yet been used isconnected and utilized only in a particular mode of operation.

Devices 13, 14, 23 can determine and store further configuration datastructures KDS with further related configuration data. Such devices 13,14, 23 can, for example, comprise various configuration data structuresfor the purposes of connecting to various apparatuses 11, 12. A devicecan, however, also have a plurality of configuration data structures forthe purposes of renewed connection to the same apparatus 11; the saidconfiguration data structures belonging, for example, to various plantconfiguration versions. Thus, one autoconfiguration can be retained forvarious plant configuration versions.

On the other hand, there are devices that can be reactivated only withthe first-time configuration data structure and the relatedconfiguration data, in the event of a renewed connection to theapparatus. Here any alteration of the configuration after the first-timeconnection of the device 13, 14, 23 to the apparatus 11, 12, 21 is notauthorized.

In one variant a configuration data structure KDS can be utilized in theauthentication phase of a subsequent communications connection. For thispurpose the configuration data structure KDS is sent along at the sametime as a parameter, or an attribute certificate, in the course of thedevice authentication. With the use of the configuration data structurein the course of an authorization it can be ensured that the device mayonly construct a communications connection in a certain configuration,and that this also can be checked at the remote station, that is to say,at the communications partner.

The configuration data structure KDS can also be used in the keyexchange phase of a subsequent communications connection. In this mannerit can be ensured, for example, that a session key is tied to anexisting configuration, and cannot inadvertently be used by the devicein the event of any change of the configuration. This is particularly ofadvantage if the configuration of a device has altered between twoautoconfiguration activities. The apparatus 21 is designed, as are theapparatuses 11 and 12, such that the functions and methods described canbe executed on them. The same is true for the devices 12, 13, 14, 23described, together with the systems 10 and 20.

In FIG. 4, a sequence is represented for a deterministicautoconfiguration by means of a flow chart. The autoconfigurationprocess begins in step 40, in that a device 12, 13, 14, 23 is pluggedinto, that is to say, is connected to, an apparatus 11, 12, 21. In step41, for example, identification data of the plugged-in device arefirstly transmitted to the apparatus 11, 12, 21, and are there checkedin accordance with, for example, a security directive. If in step 42 anydeviation of the device from the security directive is established, forexample, an error message is outputted in step 43, and no configurationis executed.

If no deviation is established in step 42 a check is made in the device13, 14, 23 and/or in the apparatus 11, 12, 21 as to whether aconfiguration data structure KDS is present in the local memory, seestep 44. If it ensues in step 45 that no configuration data structureKDS is yet present, a configuration data structure KDS is generated andstored in accordance with one of the examples cited above, see step 48.In step 49 the configuration is set up in the device and/or in theapparatus. In step 50 the autoconfiguration process is thereforecompleted. The device 13, 14, 23 can then operate together with theapparatus 11, 12, 21 in its configuration as determined.

If the device 13, 14, 23 is separated, that is to say, unplugged, fromthe apparatus 11, 12, 21, the method as described begins once again withstep 40, with a renewed plugging of the device 13, 14, 23 into theapparatus 11, 12, 21.

If the identification data, which in step 41 are transmitted to theapparatus, are already part of the configuration data structure KDS,then step 41 corresponds to step 44, and the process can then be pursuedfurther directly with step 46, namely the reading of the configurationdata structure KDS and the reactivation of the first-time configurationdata.

Thus, on the one hand the flexibility of an autoconfiguration isutilized, for example for applications in an automation environment, andat the same time stable operation of an automation plant is ensured bymeans of the first-time configuration data that have already beenchecked.

Although the present invention has been disclosed in the form ofpreferred embodiments and variations thereon, it will be understood thatnumerous additional modifications and variations could be made theretowithout departing from the scope of the invention.

For the sake of clarity, it is to be understood that the use of ‘a’ or‘an’ throughout this application does not exclude a plurality, and‘comprising’ does not exclude other steps or elements.

The invention claimed is:
 1. A method for deterministicautoconfiguration of a device in the course of a connection, the methodcomprising: providing an apparatus wherein the device is capable ofbeing connected to the apparatus, wherein there is no configuration datastructure present assigned to the apparatus and to the device before afirst-time connection of the device to the apparatus; in an event of thefirst-time connection of the device to the apparatus, generating adevice-specific configuration data structure, wherein the configurationdata structure identifies a configuration data of the device and theapparatus, the configuration data having been determined in a course ofthe first-time connection of the device to the apparatus, and storage ofthe configuration data structure in the device and/or in the apparatus,further wherein the configuration data structure comprises aconfiguration identifier, which is determined in the course of thefirst-time connection of the device to the apparatus, and in the eventof a renewed connection of the device to the apparatus, determining thefirst-time configuration data of the device and the apparatus by meansof the configuration identifier, and setting up of the device and/or theapparatus with the first-time configuration data, wherein any alterationof the configuration data structure prevents setting up of the deviceand/or the apparatus.
 2. The method as claimed in claim 1, whereinfixedly prescribed device identification information, which istransmitted from the device at least in the case of the first-timeconnection to the apparatus for the purposes of identifying the device,is recorded in the configuration data structure and the first-timeconfiguration data of the device and the apparatus are determined bymeans of the device identification information.
 3. The method inaccordance with claim 1, wherein the configuration data structurecomprises a hash value of the configuration data, and the setting up ofthe device and/or the apparatus with a reactivated configuration data isthen solely executed if the hash value of the reactivated configurationdata agrees with the hash value in the configuration data structure. 4.The method in accordance with claim 1, wherein configuration data arestored only after a successful test of the configuration data.
 5. Themethod in accordance with claim 1, wherein the configuration datastructure comprises information concerning a type of the device.
 6. Themethod in accordance with claim 1, wherein the configuration datastructure comprises a plant configuration identifier, and only aconnection of a device to an apparatus with a particular plantconfiguration identifier and/or the same plant configuration identifieris authorized.
 7. The method in accordance with claim 1, wherein theconfiguration data structure is stored in the device and/or in theapparatus only after a successful function test, and/or after asuccessful comparison of a device identification information, and/orafter a successful comparison of the configuration data with previouslyestablished data, and/or after a confirmation by an administrator. 8.The method in accordance with claim 7, wherein further configurationdata structures with further related configuration data is determinedand stored for a device.
 9. The method in accordance with claim 1,wherein in the course of a renewed connection to the apparatus, a deviceis configured solely with the first-time configuration data structureand related configuration data.
 10. The method in accordance with claim1, wherein the configuration data structure has a temporal period ofvalidity, which is prescribed by the device and/or by the apparatus. 11.The method in accordance with claim 10, wherein after an expiry of theperiod of validity, the configuration data structure is identified asblocked, or deleted.
 12. The method in accordance with claim 1, whereinthe configuration data structure has a spatial validity data, and arenewed connection of the device to the apparatus is only possible in ageographical region that corresponds to the spatial validity data. 13.The method in accordance with claim 1, wherein the configuration datastructure is used for the purposes of authenticating and/or authorizingthe device and/or the apparatus in a subsequent communicationsconnection.
 14. The method in accordance with claim 1, wherein theconfiguration data structure is used in the course of a key exchange ina subsequent communications connection of the device and/or theapparatus.
 15. The method of claim 1, wherein if alteration of theconfiguration data structure is detected in the event of a renewedconnection of the device to the apparatus an error message is outputted.16. A computer program product, comprising a computer readable storagedevice storing a computer readable program code, the computer readableprogram code comprising program commands for the purposes of executingthe method in accordance with claim
 1. 17. A system for thedeterministic autoconfiguration of a device in the course of aconnection, comprising the device and at least one apparatus, whereinthe system is configured such that: there is no configuration datastructure assigned to the at least one apparatus and to the devicebefore a first-time connection of the device to the at least oneapparatus, in the event of a first-time connection of the device to theat least one apparatus, the at least one apparatus determines a devicespecific configuration data structure, wherein the configuration datastructure identifies the configuration data of the device and the atleast one apparatus, the configuration data having been determined inthe course of the first-time connection of the device to the at leastone apparatus, and the configuration data structure is stored in atleast one of the device and the at least one apparatus, further whereinthe configuration data structure comprises a configuration identifier,which is determined in the course of the first-time connection of thedevice to the apparatus, and in the event of a renewed connection of thedevice to the at least one apparatus, at least one of the device and theat least one apparatus determine the first-time configuration data ofthe device and the at least one apparatus by means of a configurationidentifier, and are set up with the reactivated first-time configurationdata, wherein any alteration of the configuration data structureprevents set up of the device and/or the at least one apparatus.
 18. Thesystem as claimed in claim 17, wherein the device is an internalcomponent of the at least one apparatus that is plugged into the atleast one apparatus, or the device is a pluggable peripheral componentof the at least one apparatus, or the device is a network component, oran application on a network component, which is connected to the atleast one apparatus, which is a communications network with networkcomponents and/or control units.